Host interface for direct connection of an optical drive to an IDE/ATA data bus

ABSTRACT

A compact disk drive controller to control the access of information from an optical compact disk (CD) digital data storage device by a host computer using an integrated drive electronics (IDE) data bus or an industry standard architecture (ISA) data bus is disclosed. A digital signal processor (DSP) interface to the drive electronics of the CD drive, a dynamic random access memory (DRAM) controller, an error correction code (ECC) data corrector, an error detection and correction (EDC) device employing cyclical redundancy checking techniques (EDC/CRC), and a host computer interface are described.

CROSS-REFERENCE TO RELATED APPLICATIONS

This is a continuation of application Ser. No. 10/773,880, now U.S. Pat.No. 6,968,404, filed Feb. 6, 2004, which is a continuation ofapplication Ser. No. 10/082,990, now U.S. Pat. No. 6,721,828, filed Feb.25, 2002, which is a continuation of application Ser. No. 09/442,866,now U.S. Pat. No. 6,546,440, filed Nov. 18, 1999, which is acontinuation of application Ser. No. 08/673,327, now U.S. Pat. No.6,584,527, filed Jun. 28, 1996, which is a continuation of applicationSer. No. 08/264,361, now U.S. Pat. No. 5,581,715, filed Jun. 22, 1994.

BACKGROUND OF THE INVENTION

1. Field of the Invention

This invention relates generally to the access of digital data fromoptical storage media by a personal computer. Optical storage methodsallow information to be recorded and recovered from a given material byusing light. The compact disk (CD) media currently used in opticalrecording is capable of significantly higher areal density than magneticdisks. This capacity to store a large amount of information per unitarea of the media surface is a major advantage of CD technology overmagnetic disk storage techniques.

2. Prior Art

The field reliability of CD systems is yet to be determined due to therelatively short period of time this media has been in use. However,optical recording systems are expected to be more reliable than magneticdisk drives, generally referred to as hard disks, for several reasons.The optical heads used for recording and recovering information arespaced away from the disk at all times, eliminating the possibility ofhead crashes. And the optical techniques used cause no wear or tear onthe media surface during reading or transferring of information.

The reliability characteristic of optical storage media appears to beespecially advantageous where the removability and transportability ofthe media is critical. Compared to magnetic disk drives, both hard andfloppy, the operation of a CD is much less sensitive or affected by dustaccumulation on either the head or the media. And the optical methods ofreading and writing data without making physical contact with the mediasurface significantly reduces the potential for damage in removable diskapplications.

The integration of CD drives into personal computers comprises one ofthe largest markets for optical storage media applications for theforeseeable future. At present, the cost of a CD drive is a primarybarrier to the growth of this market. However, the CD-ROM (read onlymemory) standard as originally developed by Sony and Phillips has becomethe standard defining the physical characteristics and disk format fordata storage and retrieval. This format has become very popular formaking large amounts of information available to users at a relativelylow cost and there is an increasingly large library of CD-ROM titlesavailable. CD drives which are capable of writing information to the CDare much less widely used today due to their much greater cost andcomplexity.

All CD drive designs include a CD load mechanism, a spindle, driveelectronics and a controller. The drive electronics recovers data fromthe CD as directed by the controller. The controller manages the flow ofcommands, status flags and data between the host personal computer andthe CD drive electronics.

Conventional CD drive designs support the Industry Standard Architecture(ISA) bus convention and require the insertion of an interface card orhost adapter card into an ISA input/output bus slot of the host personalcomputer. These disk drive designs include a variety of proprietary andmanufacturer specific designs as well as designs that support the threevarying software driver formats used with the Small Computer SystemsInterface (SCSI) standard. These three software driver formats includeMicrosoft's Layered Device Driver Architecture, the American NationalStandards Institutes' Common Access Method, and the Advanced SCSIProgramming Interface.

A SCSI disk drive includes a controller and a SCSI slave interface. ASCSI disk drive communicates with a host computer through a SCSI hostadapter card which must be resident on the ISA bus of the host. Thereare three types of host adapter cards, namely a register compatiblecontroller, an INT 13 h compatible controller, and an installable devicedriver. These types of host adapter designs are fully explained inwidely available technical publications.

The reliance of all conventional CD drive designs exclusively on the useof the ISA input/output bus results in the additional expense of hostadapter card electronics. Furthermore, a reduction in the range ofemployment of any given computer system due to the permanent commitmentof an input/output bus slot to communication with the CD drivecontroller is a limitation in the prior art.

An alternative bus structure is available within standard personalcomputer architecture available for use with a CD drive controller. Thisstructure is referred to as integrated drive electronics with an ATattachment interface, or IDE/ATA. The American National StandardsInstitute has published this standard and it is currently widelyavailable. The term integrated drive electronics includes any drive witha controller included. For example, all SCSI drives are in fact IDEdrives. The term IDE/ATA applies to a drive if and only if its interfaceconforms to the industry standard AT attachment specification. IDE/ATAdrives do not take up an ISA input/output slot. This class of interfaceis connected by means of a dedicated 40 pin connector found on manypersonal computer mother boards.

Conventional CD drives in the prior art failed to make use of theIDE/ATA bus. However, now that the AT standard has become widely used inmany personal computers, it would be desirable to provide a CD drivewith built-in controller functionality and a standard connector. Thiswould obviate the need for an additional host adapter card andassociated electronics. Providing these electronics in addition to theCD drive itself increases the overall cost of a system using a CD drivefor data storage and retrieval and also makes a CD drive morecomplicated to install on existing personal computers in use today. Dueto the plethora of methods of ISA interface designs used in the industrytoday, compatibility issues often occur when, for example, a particularCD drive controller is tasked with communicating with another ISA busconnected peripheral device. The high frequency of incompatibility oftenprohibits the employment of the most cost efficient or highestperformance combination of devices. The present invention, a controllerfor CD drives which can be implemented with a drive using a standard ATconnector, overcomes the problems associated with the prior art as willbe made clear in the following discussions thereof.

SUMMARY OF THE INVENTION

This invention relates to a compact disk drive controller for a compactdisk drive to control the communication of digital information between acompact disk to a host computer. The compact disk drive would generallyhave it's own drive electronics comprising a digital signal processor, amicrocontroller, a random access memory, and a system controller. Thehost computer communicates with the compact disk drive controller via anIDE data bus and receives digital information from the compact disk viathe IDE data bus. The compact disk drive controller is comprised of ahost interface, connecting the host computer via the IDE data bus withthe compact disk drive controller, in order to receive data addressesand commands from the host computer and transmit digital information tothe host computer. A path for communicating data addresses and commandsfrom the host interface to the microcontroller of the drive electronicsis employed and a digital signal processor (DSP) interface connectingthe host interface and the digital signal processor of the driveelectronics, receives digital information from the compact disk andtransmits the digital information to said host interface.

The digital signal processor interface of the compact disk drivecontroller (CDDC) further comprises a descrambler to descramble andassemble the digital information received from said digital signalprocessor and store said digital information into said random accessmemory.

The digital signal processor interface of the CDDC further comprises anerror correction code circuit to perform error correction on saiddigital information. That error correction circuit could employReed-Solomon codes.

The digital signal processor interface of the CDDC further comprises acyclic redundancy checker for detecting errors in the digitalinformation after correction of the digital information by the errorcorrection code circuit.

The host interface of the CDDC may receive data addresses and commandsfrom the host computer via an ISA data bus and may communicate digitalinformation to the host computer via the ISA bus.

The host interface of the CDDC further comprises a command FIFO totransfer commands from the host computer to the system controller of thedrive electronics of the compact disk drive.

The host interface of the CDDC further comprises a configurationregister via which the host computer instructs the compact disk drivecontroller to present the digital information onto one of the ISA andIDE data buses in a data format selected from a group including 16-bitDMA, 8-bit DMA, 16-bit PIO, and an 8-bit PIO format.

A BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a CD drive configuration of the prior artwith the IDE/ATA CD drive controller of the present invention addedthereto.

FIG. 2 is a block diagram of an implementation of the present invention.

FIGS. 3 a–3 c are a pin diagram and accompanying pin-out assignments foran implementation of the present invention.

FIG. 4 is a pin description of the system controller interface of animplementation of this invention.

FIG. 5 a is a pin description of the host interface of an implementationof this invention.

FIG. 5 b is an address map of the host registers of an implementation ofthis invention.

FIG. 6 is a pin description of the DSP interface of an implementation ofthis invention.

FIG. 7 is a pin description of the subcode interface of animplementation of this invention.

FIG. 8 a is a pin description of the RAM interface of an implementationof this invention.

FIG. 8 b is a pin description for the RAM address bus of the RAMinterface of an implementation of this invention.

FIG. 9 is a pin description of miscellaneous pins of an implementationof this invention.

FIG. 10 is a description of the address register.

FIG. 11 is a description of command packet register.

FIG. 12 is a description of interface status and interface controlregisters.

FIG. 13 and FIG. 14 are descriptions of DBCL and DBCH (Data Byte/WordCounter).

FIG. 15, FIG. 16, FIG. 17 and FIG. 18 are descriptions of HEAD0 to HEAD3(Header Registers).

FIG. 19 is a list of DACH, DACL settings for various starting points.

FIG. 20 and FIG. 21 are ECC block pointer/write address counters.

FIG. 22 is a description of WAL/CTRL0 (Control-0 Register).

FIG. 23 is a description of CTRL0 DECODER OPERATION TABLE.

FIG. 24 is a description of CTRL1 (Control-1 Register).

FIG. 25 is a description of STAT0 (Status-0 Register).

FIG. 26 is a description of STAT0 BLOCK SYNC STATUS TABLE.

FIG. 27 is a description of SSTAT1 (Status-1) register.

FIG. 28 is a description of STAT2 (Status-2) register.

FIG. 29 is a description of STAT2 RMODE TABLE.

FIG. 30 is a description of STAT3/RESET (Status-3) register.

FIG. 31 is a description of CTRLW (Control-Write) register.

FIG. 32 is a description of CRTRG (Correction Retry Trigger).

FIGS. 33 through 38 are descriptions of SUBH0 to SUBH3 (SubheaderRegisters).

FIG. 39 is a description of Subheader Byte Number Table.

FIG. 40 is a description of VER (Version) register.

FIG. 41 is a description of DSPSL (DSP Selection) register.

FIG. 42 DSP SELECTION TABLE shows the settings for various DSPs.

FIG. 43 is a description of the HCON/UACL register.

FIG. 44 is a description of the DSPSL register.

FIGS. 45, 46 and 47 are descriptions of the UACL, UACH and UACUMicrocontroller-RAM Address Counter.

FIG. 48 is a description of the RAMRD/RAMWR RAM Read and Writeregisters.

FIG. 49 is a description of HDDIR Host data Direction Register.

FIG. 50 is a list of the only values that should be written toHDDIR—write bits 4, 3, 2, 1 and 0, following hardware or firmware reset.

FIG. 51 is a description of the HICTL Host Interface Control register.

FIG. 52 is a description of SUBC2 Subcode Control-2 register.

FIG. 53 is a description of the DSP Subcode Clock TABLE.

FIG. 54 is the STATS Status of subcode register.

FIGS. 55 and 56 are descriptions of DBACL and DBACH Data Transfer BlockRegisters.

FIGS. 57 and 58 are descriptions of SBKL and SBKH Subcode Write BlockRegisters.

FIGS. 59 and 60 are descriptions of WBKL and WBKH Decoder andBuffer-Write Block Counter registers.

FIG. 61 is a description of RAMCF RAM Configuration Register.

FIG. 62 is a table of RCF2, RCF1 and RCF0—bits 2, 1 and 0—RAMConfiguration.

FIG. 63 is a description of MEMCF (Memory Layout Configuration)register.

FIG. 64 is a description of MLY1 and MLY0—bits 1 and 0—Memory LayoutConfiguration.

FIG. 65 is a description of SUBCD Subcode Control register.

FIG. 66 is SBSEL1 and SBSEL0—bits 1 and 0—Subcode Format Select Table.

FIG. 67 is a description of UMISC (Miscellaneous MicrocontrollerControl) register.

FIG. 68 is a description of RSSTAT—Reset, IDE, and Subcode StatusRegister.

FIGS. 69–75 are descriptions of ATAPI Task File Registers (TR).

FIG. 69 is a description of ATFEA and ATERR.

FIG. 71 is a description of ATSPA—Spare TR.

FIG. 72 is a description of ATBLO—I/O of Byte Count Low TR.

FIG. 73 is a description of ATBHI—I/O of Byte Count High TR.

FIG. 74 is a description of ATDRS—I/O of Drive Select TR.

FIG. 75 is a description of ATCMD—Output from Command Register.

FIGS. 76–83 are descriptions of the Microcontroller to Host DataTransfer Registers.

DESCRIPTION OF A PREFERRED EMBODIMENT

Reference is now made to FIG. 1 which is a block diagram of a compactdisk (CD) drive configuration of the prior art with a CD drivecontroller of the present invention added thereto. The CD drivecontroller designed according to this invention would communicatecommand data, status signals and other data over the integrated deviceelectronics/AT attachment (IDE/ATA) bus of a personal computer. Thisinvention reduces the cost of a CD drive by eliminating the need for ahost adapter card or additional ISA bus interface electronics. Thisinvention also allows the CD drive to integrate into many personalcomputers without requiring the use of an ISA input/output bus slot.Furthermore, this invention will allow for a wider selection of personalcomputer peripheral cards, such as sound and boards, for use with agiven personal computer and CD drive. The method of the currentinvention reduces this potential for incompatibility, and permits abroad range of selection of peripheral devices.

The drive controller 10 is connected to drive electronics 12 of a CDdrive 14 and IDE/ATA bus 16 of a personal computer. The clock speed ofthe controller will be determined by crystal oscillator 11. It will beunderstood that the compact disk 18 is not a part of the presentinvention but it is shown for clarity. The CD drive includes a spindlemotor 20 for rotating the CD and an optical head 22 for reading datafrom the CD. The drive electronics of the CD drive include apreamplifier 24 which sends a signal to servo control 26 of the CD drivefor focus and tracking control. The servo control communicates with thespindle motor and optical head to position the optical head precisely toread the correct information from the CD. Digital data read from thepreamplifier goes to digital signal processor (DSP) 28 in the driveelectronics. The DSP sends subcode information as well as digital datato the drive controller of this invention. A microcontroller 29 in theCD drive electronics also communicates with the DSP and servo control ofthe drive electronics, as well as with the drive controller of thepresent invention, to control the reading of information from the CD. ADRAM 30 is coupled with the drive controller of the present inventionfor storing and buffering data via the drive controller. Data can besent to digital-to-analog convertor (DAC) 32 and peripheral 34 (such asa monitor) from the DSP or from the drive controller.

FIG. 2 is a block diagram of an implementation of the drive controller10 of the present invention. The key functional blocks are the DSP dataand subcode interfaces 36 and 37, the buffer DRAM control 38, the errorcorrection code (ECC) data corrector 40, the error detection andcorrection/cyclic redundancy checker (EDC/CRC) 42 and host control orinterface 44. The DSP data interface descrambles and assembles data fromthe DSP 28, then stores the data into the RAM. The DSP subcode interfaceassembles subcode and stores P-W data into the RAM. A DSP addresscounter 58 generates an address for each block of data stored to theDRAM from the DSP interface. The error correction circuitry would firstperform Reed-Solomon error correction on each block of data.Reed-Solomon codes are random single- or multiple-symbol errorcorrecting codes operation on symbols which are elements of a finitefield. All encoding, decoding, and correction computations are performedin the field. (See Practical Error Correction Design for Engineers,revised second edition, Cirrus Logic 1991 by Neal Glover and TrentDudley). Then, a cyclic redundancy check of the corrected data would beperformed. Since each codeword contains two parity bytes the drivecontroller of this invention can correct one error in each codeword.These ECC and EDC-CRC circuits are commonly available as hardware usedin many other applications. The host control allows the corrected datato be transferred from the RAM to the host. Diagnostic data can betransferred from the host to the RAM, allowing testing of the ECC, EDC,host control RAM and system controller. Operation of the drivecontroller is controlled by the microcontroller 29, sometimes referredto as a system controller through an 8-bit bus. The invention can decodeCD media according to the Sony-Philips standard for CD-ROM and CD-Iformats. These formats divide each 2 KB data block into two planes, eachplane containing 43 P-codewords and 26 Q-codewords. Each codewordcontains two parity bytes.

The host computer (not shown) is connected, through the IDE/ATA bus 16and associated host interface, to the microcontroller 29 of the driveelectronics of the CD drive and the host control 44. The host interfaceprovides 8/16 bit peripheral input/output (PIO) and direct memory access(DMA) transfers of data to the host personal computer. The outputbuffers 54 of the invention can directly drive an IDE/ATA bus. The hostinterface also contains control and transfer status registers 56accessible by the host. The design of the present invention allows thetransfer of diagnostic data from the host to the RAM, allowing testingof the error correction circuitry, the host interface, the RAM itselfand the system controller of the drive electronics.

The DRAM controller is connected to DRAM 50. The DRAM controller, underthe direction of the host interface, accomplishes the transfer of datato the host and the error correction operations so as to insure anuninterrupted flow of data from the buffer RAM. The DRAM receivesinformation from the DSP of the drive electronics via the DSP data andsubcode logic interfaces. The DRAM also receives address informationfrom the host microprocessor address counter 60, as well as receivescorrected and addressed information from an ECC EDC address generator 52which is connected with the error correction circuit ECC and the cyclicredundancy checker EDC CRC. Additionally, the DRAM stores header andsubheader information to the header/subheader register 62.

Thus, the drive controller 10 accepts digital data from the CD drive'selectronics 12, particularly the microcontroller 29 and DSP 28, in aserial stream, descrambles the data, and assembles it into 8-bit bytes.The controller 10 then stores the data into the DRAM buffer 50. Theerror correction and detection operations performed by the ECC 40 andEDC CRC 42 on each sector of data are managed by the DRAM controller 38,which insures, through the direction of the host interface or control44, that a sector of data is being corrected while the transfer ofpreviously corrected sectors of data is occurring in real-time andwithout interrupting the flow of data from the drive controller 10 tothe IDE bus 16. The flow of data is controlled by a data path controller64. Therefore, the controller 10 of the present invention communicatescorrected command data, status signals, and other corrected data overthe IDE bus 16 of the host computer, eliminating the need for a hostadapter card or additional ISA bus interface electronics, to reduce thecost of the CD drive 14. The invented controller 10, additionally,allows the CD drive 14 to integrate into many different personalcomputers, without requiring the use of an ISA input/output bus slot ofthe host computer.

FIGS. 3 a–3 c are a pin diagram and accompanying pin-out assignments foran implementation of the present invention. The functions performed bythis implementation will become clear by the following discussion.

FIG. 4 is a pin description of the system controller interface of animplementation of this invention. The system controller is themicrocontroller that controls the operation of the IDE CD-ROMcontroller. The system controller interface contains an 8-bitbi-directional data transfer bus and is compatible with mostmicrocontrollers.

FIG. 5 a is a pin description of the host interface of an implementationof this invention. This invention will support the ATAPI CD-ROMspecification for an IDE CD-ROM interface. The drive controller candrive IDE interface signal lines directly. The host interface contains a12 bytes command packet FIFO (first in first out) and IDE registers.These are used to direct or command the host interface by the hostcontroller and to inform the host controller as to the precise status ofthe drive electronics. The host interface block also contains a dataFIFO register for transferring data from the DRAM buffer to the host andvice versa. FIG. 5 b is an address map of the host registers of animplementation of this invention. The logic conventions are as follows:A=signal asserted, N=signal negated.

FIG. 6 is a pin description of the DSP interface of an implementation ofthis invention. This invention is designed to work with various DSPchips, which are selected using the DSPSL register. Serial data isreceived from the DSP. FIG. 7 is a pin description of the subcodeinterface of an implementation of this invention. P-W subcodeinformation provided serially by the DSP will be stored into the datablock of the DRAM simultaneously. This invention will support severaldifferent subcode interface protocols, which are selected using theSUBCD register. The command FIFO register COMIN is used to direct thehost interface by the host controller.

FIG. 8 a is a pin description of the RAM interface of an implementationof this invention. This embodiment allows users to use conventional 128KB/256 KB DRAM. FIG. 8 b is a pin description for the RAM address bus ofthe RAM interface of an implementation of this invention. Note thatseveral RAM address bits are reserved for future support of larger RAMsizes. FIG. 9 is a pin description of miscellaneous pins of animplementation of this invention.

Microcontroller Registers

The following map and description of the registers of an embodiment ofthis invention is intended for use in designs supporting the followingconfigurations:

1. Type of RAM: 256K×4×1 DRAM or 256K×4×2 DRAM

2. Type of Host Interface: ATA (IDE) plus ATAPI CD-ROM

FIG. 10 is a description of the address register. The internal registersare subsequent R/W operation. The AR is read or written by themicrocontroller if URS=0. If URS=1, the register addressed by the AR isread or written.

Except for address 00h (COMIN/SBOUT), the 4 least significant bits (bits0–3) of the AR are automatically incremented following each read orwrite to any register For example, if the AR has been set to 2Ch, the ARautomatically increments according to the following sequence during 18consecutive reads or writes (with URS=1): 2Ch, 2Dh, 2Eh, 2Fh, 20h, 21h,22h, 23h, 24h, 25h, 26h, 27h, 28h, 29h, 2Ah, 2Bh, 2Ch, 2Dh.

Note: The AR does not automatically increment from 00h to 01h.Consecutive accesses to address 00h will repeatedly read (COMIN) orwrite (SBOUT). For example if the AR has been set to 0Ch, the ARautomatically increments according to the following sequence during 7consecutive reads or writes (with URS=1): 0Ch, 0Dh, 0Eh, 0Fh, 00h, 00h,00h.

FIG. 11 is a description of command packet register. This registeraccesses the 12-byte Packet FIFO which receives commands or data fromthe host. The data transfer end interrupt (DTEIb) flag in the IFSTATregister is active (set to 0) while the 12-byte Packet FIFO is full. Thecommand interrupt (CMDIb) flag in the IFSTAT register is active (set to0) while one or more bytes from the host are present in the Packet FIFO.If an access from COMIN is attempted while the FIFO is empty, the valueFfh will be read.

Normally, flag DTEIb is used for receiving 12-byte packet commands fromthe host, and flag CMDIb is used for receiving data from the host (whichmay not be 12-bytes). Registers ATBHI and ATBLO (addresses 34h and 35h)can be used to control the number of consecutive bytes of DATA writteninto the Packet FIFO by the host. However, ATBHI and ATBLO should not beused to control the number of COMMAND bytes. Command or data writes fromthe host to the data port (1F0) are stored in the Packet FIFO if controlbit Scod in register HICTL (20h.2) is set high. Note: An access to theCOMIN register (00h) does not increment the AR.

UNUSED (01h-write) writes to address 00h in the controller accessed theSBOUT (status byte output register. However, SBOUT is not useful forATAPI operations. Address 00h should not be written to. Note: An accessto address 00h does not increment the AR.

FIG. 12 is a description of interface status and interface controlregisters.

IFSTAT (Interface Status Register) holds the decoder and host interfacestatus bits.

CMDIb—bit 7—Command Interrupt flag is active-low with a logical 0indicating an interrupt flag. “0” indicates that there are one or morebytes present in the Packet FIFO and “1” indicates that the Packet FIFOis empty. Flag CMDIb is used for receiving data from the host, which maynot be 12-bytes. For receiving 12-byte packet commands, flag DTEIb inregister IFSTAT is used instead. CMDIb is automatically cleared (setto 1) after the last byte in the Packet FIFO is read. If control bitCMDIEN in the IFCTRL register (01h.7) is set high, pin UINTb (themicrocontroller interrupt) will be active-low whenever the CMDIb flag isactive-low.

DTEIb—bit 6—Data-Transfer-End Interrupt flag is active-low with alogical 0 indicating an interrupt flag. “0” indicates that a host readfrom the Data FIFO or external RAM, or a 12-byte host write to thePacket FIFO (Packet FIFO full), is complete and “1” indicates that theinterrupt flag has been cleared. DTEIb is automatically cleared when themicrocontroller writes to the DTACK register (07h). If control bitDTEIEN in the IFCTRL register (01h.6) is set high, pin UINTb (themicrocontroller interrupt) will be active-low whenever the DTEIb flag isactive-low.

DECIb—bit 5—Decoder Interrupt flag is active-low with a logical 0indicating an interrupt flag. “0” indicates that the decoder hasfinished processing a block and “1” indicates that the interrupt flaghas been cleared. When DECIb changes to active-low, the header registers(HEAD0-3), ECC block pointer registess (PTL, PTH), and status registers(STAT0-3) are ready to be read. If the ECC or EDC is enabled, DECIbchanges to active-low at the completion of the EDC phase. If the ECC andEDC are disabled (write-only or disk-monitor operation), DECIb changesto active-low after the header registers (HEAD0-3) are ready. DECIb isautomatically cleared (to 1) when the microcontroller reads the STAT3register (0Fh).

X—bit 4 is undefined, and may return a 0 or 1.

DTBSYb—bit 3—Data Transfer Busy flag is active-low with a logical 0indicating a busy flag. “0” indicates that a data-transfer is in processand “1” indicates that no data-transfer in process. DTBSYb changes toactive-low when the microcontroller writes to the data transfer trigger(DTTRG). DTBSYb is automatically cleared (to 1) when the host BEGINS toread the last byte to be transferred from the Data FIFO or external RAM.

X—bit 2 is undefined, and may return a 0 or 1. SBOUT is not useful forATAPI operation.

DTENb—bit 1—Date Enable is active-low with a logical 0. “0” indicatesthat a data-transfer is in process and “1” indicates that nodata-transfer is in process. After DTTRG is set, DTENb changes toactive-low when the Data FIFO is ready to be read by the host. DTENb isautomatically cleared (to 1) after the host reads the last byte to betransferred from the Data FIFO or external RAM.

X—bit 0 is undefined, and may return a 0 or 1. SBOUT is not useful forATAPI operation.

IFCTRL (Interface Control Register) provides control of themicrocontroller interrupt and host interface.

CMDIEN—bit 7—Command Interrupt Enable “1” allows pin UINTb (themicrocontroller interrupt pin) to become active-low whenever the CMDIbflag in register IFSTAT is active-low. “0” inhibits the CMDIb flag fromactivating pin UINTb. CMDIEN controls the operation of pin UINTb.However, CMDIEN does not clear the interrupt request or control theCMDIb flag. CMDIEN is cleared to 0 by hardware reset or firmware reset.

DTEIEN—bit 6—Data-Transfer-End Interrupt Enable “1” allows pin UINTb(the microcontroller interrupt pin) to become active-low whenever theDTEIb flag in register IFSTAT is active-low. “0” inhibits the DTEIb flagfrom activating pin UINTb. DTEIEN controls the operation of pin UINTb.However, DTEIEN does not clear the interrupt request or control theDTEIb flag. DTEIEN is cleared to 0 by hardware reset or firmware reset.

DECIEN—bit 5—Decoder Interrupt Enable “1” allows pin UINTb (themicrocontroller interrupt pin) to become active-low whenever the DEClbflag in register IFSTAT is active-low. “0” inhibits the DEClb flag fromactivating pin UINTb. DECIEN controls the operation of pin UINTb.However, DECIEN does not clear the interrupt request or control theDEClb flag. DECIEN is cleared to 0 by hardware reset or firmware reset.

DOUTEN—bit 1—Data Output Enable “1” enables host data reads from theData FIFO or external RAM, or host writes to the Packet FIFO. “0”inhibits data transfers to the Data FIFO, external RAM, or Packet FIFO.Clearing DOUTEN (to 0) aborts data transfers to the FIFOs or externalRAM. DOUTEN is cleared to 0 by hardware reset or firmware reset.

Unused Bits—bits 4, 3, 2, and 0 should only be set to 0.

FIG. 13 and FIG. 14 are descriptions of DBCL and DBCH (Data Byte/WordCounter) that form a 12-bit counter that controls or monitors the numberof bytes or words transferred from the Data FIFO or external RAM to theHost. For 16-bit transfers, the number of WORDS minus one should beloaded into this counter. For 8-bit transfers, the number of BYTES minusone should be loaded. DBCH should always be written after DBCL iswritten, and zero should be written into bits 7-4 of DBCH. During thedata transfer, the counter is decremented by one each time the hostreads a word or byte. When reading DBCH, bits 7-4 each indicate thestatus of the data-transfer-end interrupt (DTEI), and have the samefunction (but opposite polarity) as the DTEIb flag in register IFSTAT.DBCL and DBCH are undefined following hardware reset or firmware reset.

FIG. 15, FIG. 16, FIG. 17 and FIG. 18 are descriptions of HEAD0 to HEAD3(Header Registers). Normally, these registers provide the header of eachCD-ROM block, and are used to find the starting block during a diskseek. If control bit DECEN in register CTRL0 (0Ah.7) is enabled, thefirst four bytes (bytes 12–15) following each data sync areautomatically stored in the header registers (HEAD0-3). Duringdisk-monitor operation (see the description of register CTRL0),uncorrected header bytes are taken directly from incoming serial data.If the incoming serial data is buffered, header bytes are taken from thebuffer RAM, and are corrected if mode 1 is selected and ECC is enabled.In either case, HEAD0-3 should be read soon after the decoder interruptoccurs (bit DEClb in register IFSTAT becomes 0). HEAD0-3 remains validuntil the next sync occurs (see the description of register STAT3 forchecking the valid time period). Generation of checkbytes during theauthoring of CD-ROM disks includes ECC coverage of the header bytes formode 1 blocks, but not for mode 2 blocks. Therefore if ECC is enabled,the header bytes are not valid unless the proper mode is selected usingcontrol bit MODRQ in register CTRL1 (0Bh.3). Operation of a mode 2 diskwith mode 1 ECC causes the header bytes to be erased. By setting controlbit SHDREN in register CTRL 1 high, HEAD0-3 can be used to providesubheader bytes instead of header bytes. However, it is more convenientto use registers SUBH0-3 (14h–17h), which are not controlled by bitSHDREN, for this purpose. See the description of SUBH0-3 for subheaderinformation. Subheaders in HEAD0-3 follow the same format and operationas subheaders in SUBH0-3. HEAD0-3 are undefined following hardware resetor firmware reset.

FIG. 19 is a list of DACH, DACL settings for various starting points.DACL and DACH are Data Address Counters. DACL and DACH form a 16-bitcounter that controls the buffer RAM address for transfers to the host.The microcontroller writes the starting address that corresponds to therequired starting point in the CD-ROM block. After the starting addressis set and register DTTRG is triggered, DACL and DACH are incrementedautomatically each time a byte or word is read by the host. The firstbyte of User Data is located at address 00h. DACH should always bewritten after DACL is written. For proper addressing, the mode of theCD-ROM block should be selected using control bit MODRQ in registerCTRL1 (0Bh.3). DACL and DACH control the RAM address relative to thebeginning of the block. The block number should also be specified, usingdata block registers DBACL and DBACH (24h and 25h). DACL and DACH areundefined following hardware reset or firmware reset.

DTTRG (Data Transfer Trigger) triggers the host transfer logic andprepares the Data FIFO, causing flag DTBSYb in register IFSTAT (01h.3)to become active-low. Before setting or triggering any data transferregisters, control bit DOUTEN in register IFCTRL (01h.1) should beenabled. In the case of a host data read from the buffer RAM, triggeringthe transfer logic automatically fills the FIFO with data from the RAM.The count, RAM starting address, and block number should be set usingregisters DBCL, DBCH, DACL, DACH, DBACL, and DBACH (02h, 03h, 04h, 05h,24h, and 25h) before triggering DTTRG. Flag DTENb in register IFSTAT(01h.1) becomes active-low when the FIFO first becomes ready. Themicrocontroller can also load registers UDTA0-UDTA7, allowing host datareads (up to 8-bytes) from the microcontroller without using the bufferRAM. In this case the byte count, microcontroller data enable, and databytes should be set using registers DBCL, DBCH, HDDIR, and UDTA0-7 (02h,03h, 1Fh.6, and 40h-47h) before triggering DTTRG. After triggeringDTTRG, trigger bit UDTRG in register HDDIR (1Fh.7) should be toggled to1 followed by 0. For this type of transfer, flag DTENb in registerIFSTAT (01h.1) has no meaning. Trigger DTTRG is not used for host writesto the Packet FIFO.

DTACK (Data Transfer Acknowledge) clears flag DTEIb to 1 in registerIFSTAT (01h.6) and also clears the corresponding microcontrollerinterrupt (if enabled), terminating the data transfer sequence.

FIG. 19 and FIG. 20 are ECC block pointer/write address counters. PTLand PTH form a pointer used by the ECC logic, and contain the 12 leastsignificant address bits of the first header byte of the CD-ROM blockthat is being corrected. Due to the DRAM page organization of oneembodiment of the controller, the value of PTH,PTL will always be00,00h, making it unnecessary to read or write PTL or PTH. The startinglocation of each block is controlled by write block counter registersWBKL and WBKH (28h and 29h). Error correction is processed on the blockbefore that indicated in the write block counter (WBKH,WBKL—1). Thecontroller organizes the DRAM into 2048-byte pages, allowing PTL and PTHto remain unchanged. PTL and PTH are undefined following hardware resetor firmware reset.

WAL and WAH (Write Address Counter) form a 16-bit counter used by thewrite buffering logic. At the end of each data sync, WAH,WAL areautomatically set to 00,00h. Following each word (two bytes) of writebuffering into the external RAM, WAL and WAH are automaticallyincremented by two. Due to the DRAM page organization of the controller,WAL and WAH control the write location within each CD-ROM block, and arealways set to 00,00h after each data sync. The starting location of eachblock is controlled by write block counter registers WBKL and WBKH (28hand 29h). It is not necessary to read or write WAL or WAH, except fordebugging purposes. Because WAL and WAH are automatically incrementedwhenever control bits DECEN and WRRQ are enabled in register CTRL0(0Ah.7 and 0Ah.2), WRRQ should be disabled before reading the writeaddress counter. WAH,WAL are cleared to 00,00h by hardware reset orfirmware reset.

FIG. 22 is a description of WAL/CTRL0 (Control-0 Register). Thisregister provides control of the ECC and write buffering logic.

DECEN—bit 7—Decoder Enable “1” enables the decoding functions, allowingcontrol bits E01RQ, AUTORQ, WRRQ, QRQ, and PRQ to control the ECC andwrite buffering logic. “0” disables the decoding functions, overridingcontrol bits E01RQ, AUTORQ, WRRQ, QRQ, and PRQ. Changes to DECEN controlthe CD-ROM blocks following the next data sync. DECEN is cleared to 0 byhardware reset or firmware reset.

E01RQ—bit 5—Error Detect and Correct Request “1” enables the errorcorrection and detection (ECC and EDC) logic to process the followingCD-ROM blocks, according to the settings of QRQ and PRQ. “0” disablesthe ECC and EDC logic. Changes to E01RQ control the CD-ROM blocksfollowing the next data sync. If both QRQ and PRQ are enabled, theECC/EDC sequence is Q-codewords, P-codewords, EDC-codeword. If QRQ isenabled but PRQ is disabled, the sequence is Q-codeword, EDC-codeword.If QRQ is disabled but PRQ is enabled, the sequence is P-codeword,EDC-codeword. If both QRQ and PRQ are disabled, only the EDC-codeword ischecked. Normally, QRQ and PRQ are enabled whenever E01RQ is enabled inorder to provide maximum correction capability. E01RQ is cleared to 0 byhardware reset or firmware reset.

AUTORQ—bit 4—Automatic Correction Request “1” enables automatic errorcorrection for mode 2 CD-ROM blocks, according to the setting of theFORM bit in the Subheader byte of each block. “0” disables automaticerror correction for mode 2 CD-ROM blocks. In this case, errorcorrection for mode 2 blocks is controlled by control bit FORMRQ inregister CTRLI (0Bh.2). Changes to AUTORQ control the CD-ROM blocksfollowing the next data sync. AUTORQ does not control error correctionin mode 1. AUTORQ is cleared to 0 by hardware reset or firmware reset.

WRRQ—bit 2—Write Buffer Request “1” enables writes of incoming serialdata to the external buffer RAM automatically incremented when writesare enabled. “0” disables writes of incoming serial data to the externalbuffer DRAM.

If control bit SWEN is enabled in register CTRLW (10h.6), changes toWRRQ control writes following the next data sync. If SWEN is disabled,changes to WRRQ control writes immediately. Both WRRQ and SWEN arecleared to 0 by hardware reset or firmware reset.

QRQ—bit I—codeword Correction Request “1” enables error correction ofQ-codewords, allowing one error to be located and corrected within eachQ-codeword. “0” disables error correction of Q-codewords. Changes to QRQcontrol the CD-ROM blocks following the next data sync. QRQ is clearedto 0 by hardware reset or firmware reset.

PRQ—bit 0—P-codeword Correction Request “1” enables error correction ofP-codewords, allowing one error to be located and corrected within eachP-codeword. “0” disables error correction of P-codewords. Changes to PRQcontrol the CD-ROM blocks following the next data sync. PRQ is clearedto 0 by hardware reset or firmware reset.

FIG. 23 is a description of CTRL0 DECODER OPERATION TABLE. NOTE: Forrepeated correction, see the description of register CRTRG (11h). Forbuffered-disk-monitor, see the description of control bit ROWEN inregister CTRLW (10h.7).

FIG. 24 is a description of CTRL1 (Control-1 Register). This registerprovides control of the ECC and data sync logic.

SYIEN—bit 7—Sync Insertion Enable “1” enables sync insertion, allowingthe internal sync counter to provide timing if the block sync pattern inthe incoming serial data contains errors. “0” disables sync insertion.By enabling both SYIEN and SYDEN, the internal sync counter canautomatically provide timing if the sync pattern contains errors, andalso re-synchronize whenever a new sync pattern is detected. SYIEN iscleared to 0 by hardware reset or firmware reset.

SYDEN—bit 6—Sync Detection Enable “1” enables sync detection, allowingthe internal sync counter to re-synchronize whenever a block syncpattern is detected in the incoming serial data. “0” disables syncdetection. SYDEN is cleared to 0 by hardware reset or firmware reset.

DSCREN—bit 5—Descrambler Enable “1” enables the CD-ROM data descrambler.“0” disables the CD-ROM data descrambler. Disabling the descrambler isuseful for reading uncompressed (Red Book) audio, or for debugging.Changes to DSCREN control the descrambler immediately. DSCREN is clearedto 0 by hardware reset or firmware reset.

COWREN—bit 4—Correction Write Enable “1” enables bytes corrected by theECC logic to be written to the external RAM. “0” disables bytescorrected by the ECC logic to be written to the RAM. By disablingCOWREN, flags CRCOK and CBLK in registers STAT0 (0Ch.7) and STAT3(0Fh.5) can be used to determine disk error rates. Changes to COWRENcontrol the CD-ROM blocks following the next data sync. COWREN iscleared to 0 by hardware reset or firmware reset.

MODRQ—bit 3—Mode Request “1” sets the error correction mode used by theECC logic to mode 2. “0” sets the error correction mode used by the ECClogic to mode 1. After determining the mode from the incoming serialdata, control bit MODRQ must be set by the microcontroller. The raw modedata from the headers of the incoming serial data should be read frombits RMOD3-0 in register STAT2 (0Eh.7-4). If MODRQ is not set properly,the ECC logic will mis-correct. Note that operation of a mode 2 diskwith mode 1 correction causes the header bytes to be erased. MODRQ iscleared to 0 by hardware reset or firmware reset. Generation ofcheckbytes during the authoring of CD-ROM disks includes ECC coverage ofthe header bytes for mode 1 blocks, but not for mode 2 blocks.Consequently, the mode byte in a mode 2 disk is not corrected. Modechanges are separated by pre-gap and post-gap blocks and track numbers.Changes to MODRQ control the CD-ROM blocks following the next data sync.MODRQ is cleared to 0 by hardware reset or firmware reset.

FORMRQ—bit 2—Form Request “1” sets the form to 2, disabling the mode 2ECC logic (but EDC is enabled). “0” sets the form to 1, enabling themode 2 ECC logic. If control bit AUTORQ is enabled in register CTRL0(0Ah.4), the setting of FORMRQ is not used by the ECC logic. FORMRQ isnot used by the ECC logic if mode 1 is selected (control bit MODRQ setto 0 in register CTRL0). Changes to FORMRQ control the CD-ROM blocksfollowing the next data sync. FORMRQ is cleared to 0 by hardware resetor firmware reset.

MBCKRQ—bit 1—Mode Byte Check Request “1” enables checking of the modebyte. “0” disables checking of the mode byte. While checking of the modebyte is enabled, if the mode in the header of the incoming serial datadoes not match that selected by control bit MODRQ, ECC is disabled forthe block and the NOCOR flag is set in register STAT0 (0Ch.5). Changesto MBCKRQ control the CD-ROM blocks following the next data sync. MBCKRQis cleared to 0 by hardware reset or firmware reset.

SHDREN—bit 0—Subheader Read Enable “1” selects subheader bytes to beprovided by registers HEAD0-3 (04h-07h). “0” selects header bytes to beprovided by registers HEAD0-3. By setting SHDREN high, HEAD0-3 can beused to provide subheader bytes instead of header bytes. However, it ismore convenient to read the subheader from registers SUBH0-3 (14h-17h),which are not controlled by SHDREN. Changes to SHDREN control reads ofHEAD0-3 immediately. SHDREN is cleared to 0 by hardware reset orfirmware reset.

FIG. 25 is a description of STAT0 (Status-0 Register). This registerprovides status of the ECC, write buffering, and data sync logic.

CRCOK—bit 7—Cyclic Redundancy Check OK. Flag CRCOK can becomeactive-high only if the error detection (EDC) logic is enabled. Thisoccurs automatically if correction or write-only decoder operations areselected (see the CTRL0 Operation Table) and “1” indicates that thecyclic redundancy check passed during the last ECC/EDC sequence. “0”indicates that the cyclic redundancy check failed during the lastECC/EDC sequence. Flag CRCOK becomes valid when flag DECIb in registerIFSTAT (01h.5) changes to active-low, and remains valid until the nextblock sync. See the description of flag VALSTb in register STAT3 (0Fh.7)to determine timing of the next sync. CRCOK is cleared to 0 by hardwarereset or firmware reset.

ILSYNC—bit 6—Illegal Sync flag can become active-high only if syncdetection is enabled by control bit SYDEN in register CTRL1 (0Bh.6). Inthis case, occurrence of illegal sync re-synchronizes the internal synccounter. “1” indicates that a sync pattern was detected earlier thanexpected (less than 2352 bytes after the last detected or insertedsync). “0” indicates that no early sync pattern was detected. FlagILSYNC becomes valid when flag DEClb in register IFSTAT (01h.5) changesto active-low, and remains valid until the next block sync. ILSYNC iscleared to 0 by hardware reset or firmware reset.

NOSYNC—bit 5—No Sync flag can become active-high only if sync insertionis enabled by control bit SYIEN in register CTRL1 (0Bh.7). In this case,the internal sync counter will provide timing when the sync pattern ismissing or has errors. “1” indicates that a sync pattern was notdetected when expected (expected sync to occur 2352 bytes after the lastdetected or inserted sync). “0” indicates that a sync pattern wasdetected when expected. Flag NOSYNC becomes valid when flag DECIb inregister IFSTAT (01h.5) changes to active-low, and remains valid untilthe next block sync. NOSYNC is cleared to 0 by hardware reset orfirmware reset.

LBLK—bit 4—Long Block flag can become active-high only if sync insertionis disabled by control bit SYIEN in register CTRL 1 (0Bh.7). In thiscase, the internal sync counter will not provide timing when the syncpattern is missing or has errors. However, only 2352 bytes of incomingserial data will be written to the external RAM. “1” indicates that async pattern was not detected when expected (expected sync to occur 2352bytes after the last detected sync). “0” indicates that a sync patternwas detected when expected. Flag LBLK becomes valid when flag DECIb inregister IFSTAT (01h.5) changes to active-low, and remains valid untilthe next block sync. LBLK is cleared to 0 by hardware reset or firmwarereset.

WSHORT—bit 3—Word Short “1” indicates that the incoming serial data rateexceeds the capability of the write buffering logic. “0” indicates thatthe incoming serial data rate was OK. The WSHORT error flag becomesvalid immediately after the excessive rate is detected. This error isusually caused by hardware problems, and must be corrected for propercontroller operation. WSHORT is cleared to 0 by hardware reset orfirmware reset.

SBLK—bit 2—Short Block flag can become active-high only if syncdetection is disabled by control bit SYDEN in register CTRLI (0Bh.6). Inthis case, occurrence of illegal sync will not re-synchronize theinternal sync counter. “1” indicates that a sync pattern was detectedearlier than expected (less than 2352 bytes after the last insertedsync). “0” indicates that no early sync pattern was detected. Flag SBLKbecomes valid when flag DECIb in register IFSTAT (01h.5) changes toactive-low, and remains valid until the next block sync. SBLK is clearedto 0 by hardware reset or firmware reset.

UCEBLK—bit 0—Uncorrectable Errors in Block flag can become active-highonly if the error correction (ECC) logic is enabled (Q-P, Q, orP-correction decoder operation selected). “1” indicates that one or moreerror bytes could not be corrected during the last ECC sequence. “0”indicates that no error bytes remained after the last ECC sequence. FlagUCEBLK becomes valid when flag DECIb in register IFSTAT (01h.5) changesto active-low, and remains valid unti ue next block sync. UCEBLK iscleared to 0 by hardware reset or firmware reset.

FIG. 26 is a description of STAT0 BLOCK SYNC STATUS TABLE.

FIG. 27 is a description of SSTAT1 (Status-1) register. This registerprovides erasure flags for the header and subheader bytes of the CD-ROMblock. The erasure flags are provided through input pin C2PO.

HDERA—bit 4—Header Erasure “1” indicates that the erasure flag was setfor one or more header bytes. “0” indicates that no erasure flags wereset for the header bytes.

SHDERA—bit 0—Subheader Erasure “1” indicates that the erasure flag wasset for both bytes in one or more subheader byte-pairs. “0” indicatesthat no erasure flags were set for both bytes in the subheaderbyte-pairs. During disk-monitor operation (see the description ofregister CTRL0), erasures are read directly from incoming C2PO flags. Ifthe incoming serial data (from pin DSTATA) is buffered, the incomingC2PO flags are held and become available in STAT1 one block later,matching the one block delay of the buffered header and subheaders. Ineither case, HDERA and SHDERA become valid when flag DECIb in registerIFSTAT (01h.5) changes to active-low, and remain valid until the nextblock sync.

FIG. 28 is a description of STAT2 (Status-2) register. This registerprovides mode and form information of the CD-ROM block.

FIG. 29 is a description of STAT2 RMODE TABLE. RMOD3-RMOD0—bits 7–4—RawMode provide mode information from the incoming serial data, during bothbuffer RAM and disk-monitor operation. Because RMOD3-RMOD0 cannot bechanged by the ECC logic, they should be used for determining the modeof the CD-ROM block, according to the figure. N can be any numberbetween 1 and 1 Fh. RMOD3-RMOD0 become valid when flag DECIb in registerIFSTAT (01h.5) changes to active-low, and remain valid until the nextblock sync. RMOD3-RMOD0 are cleared to 0 by hardware reset or firmwarereset.

MODE—bit 3—Selected Mode flag provides the value of bit MODRQ inregister CTRL1 (0Bh.3). “1” indicates that bit MODRQ is set high (mode-2selected). “0” indicates that bit MODRQ is set low (mode-1 selected).Flag MODE becomes valid when flag DECIb in register IFSTAT (01h.5)changes to active-low, and remains valid until the next block sync. FlagMODE is cleared to 0 by hardware reset or firmware reset.

NOCOR—bit 2—No Correction flag indicates whether error correction wasperformed NOCOR is valid only if control bit E01RQ, and QRQ or PRQ, areenabled in register CTRL0 (0Ah.5, 0Ah.1, 0Ah.0). “1” indicates that thelast ECC/EDC sequence was aborted. “0” indicates that the last ECC/EDCsequence completed. The ECC/EDC sequence is aborted, and flag NOCOR sethigh, for the following reasons: Mode mismatch or erasure detected whilecontrol bit MBCKRQ is enabled in register CTRL1 (0Bh.1): A mode mismatchoccurs if the mode in the header of the incoming serial data does notmatch that selected by control bit MODRQ in register CTRL1 (0Bh.3). Amode erasure occurs if the incoming C2PO flag is set for the fourthheader byte, indicating unreliable mode data. Form 2 enabled while ECClogic is set to mode 2: Form 2 blocks cannot be corrected. Form 2 can beenabled by control bit FORMRQ in register CTRL1 (0Bh.2), or by the FORMbit in the Subheader byte if control bit AUTORQ is enabled in registerCTRL0 (0Ah.4). FORM bit erasures while ECC logic is set to mode 2 andAUTORQ is enabled: A form bit erasure is detected if the incoming C2POflags are set for both FORM bits in the Subheader bytes. Illegal syncoccurs while control bit SYDEN is enabled in register CTRL1 (0Bh.6),indicating that a sync pattern was detected earlier than expected.Control bit COWREN set low in register CTRL1 (0Bh.4). Flag NOCOR becomesvalid when flag DEClb in register IFSTAT (01h.5) changes to active-low,and remains valid until the next block sync. Flag NOCOR is cleared to 0by hardware reset or firmware reset.

RFORM 1—bit 1—Raw Form Erasure “1” indicates that a form bit erasure wasdetected (a form bit erasure is detected if the incoming C2PO flags areset for both FORM bits in the Subheader bytes. “0” indicates that a formbit erasure was not detected. RFORM1 becomes valid when flag DEClb inregister IFSTAT (01h.5) changes to active-low, and remains valid untilthe next block sync. RFORM1 is cleared to 0 by hardware reset orfirmware reset.

RFORM0—bit 0—Raw Form Bit “1” indicates that the FORM bit was high inthe Subheader bytes of the incoming serial data. “0” indicates that theFORM bit was low in the Subheader bytes of the incoming serial data.RFORM0 becomes valid when flag DEClb in register IFSTAT (01h.5) changesto active-low, and remains valid until the next block sync. RFORM0 iscleared to 0 by hardware reset or firmware reset.

UNUSED (0Eh-write) SBOUT is not useful for ATAPI. Address 0Eh should notbe written to.

FIG. 30 is a description of STAT3/RESET (Status-3) register. Thisregister provides status of the ECC logic. Reading STAT3 clears flagDECIb to 1 in register IFSTAT (01[b]h.6), and clears any active decoderinterrupt.

VALSTb—bit 7—Valid Status flag indicates the valid period during whichthe following header, pointer, and status registers can be read by themicrocontroller: HEAD0-3 (04h-07h), PTL and PTH (08h-09h), STAT0-3(0Ch-0Fh), SUBH0-3 (14h-17h), and WBKL and WBKH (28h and 29h). “1”indicates that the header, pointer, and status registers contain validdata, and are ready to be read. “0” indicates that the header, pointer,and status registers are not valid. Flag VALSTb becomes active-low whenflag DEClb (decoder interrupt) in register IFSTAT (01h.5) changes toactive-low, and returns?high when the next block sync occurs (detectedor inserted). Reading STAT3 does not change VALSTb. VALSTb is cleared to1 by hardware reset or firmware reset.

CBLK—bit 5—Corrected Block flag is valid only if the error correction(ECC) logic is enabled (Q-P,Q, or P-correction decoder operationselected). “1” indicates that one or more error bytes were correctedduring the last ECC sequence. “0” indicates that no bytes were correctedduring the last ECC sequence. Flag CBLK becomes valid when flag DEClb inregister IFSTAT (01h.5) changes to active-low, and remains valid untilthe next block sync. CBLK is cleared to 0 by hardware reset, firmwarereset, or by disabling WRRQ in register CTRL0 (0Ah.2).

RESET (Firmware Reset) activates firmware reset. Firmware reset clearsmost of the controller logic. However, to avoid disturbing importantlogic, firmware reset does not clear certain functions. The followinglist shows the differences between hardware reset (which clears all ofthe controller functions) and firmware reset. Functions NOT cleared byfirmware reset: Clock stop logic controlled by input pin CLKSTP,register XTAL (1Ah) and output pin MCK, register DSPSL (1Bh), flag CS13of register HDDIR (1Fh.6), register HICTL, register SUBC2 (21h),register RAMCF (2Ah), register MEMCF (2Bh), register SUBCD (2Ch),register UMISC (2Eh), register RSSTAT flags SRST, CMD, DIAGCMD, PARINT,RST, URST, and HRST (2Fh.7-5,3-0), R/W bit DRV in register ATDRS (36h)and in the ATAPI Drive Select Register, and control bits SRST and nIENin the ATAPI Device Control Register. Flag URST of register RSSTAT(2Fh.1) is set by firmware reset (see description of register RSSTAT).

FIG. 31 is a description of CTRLW (Control-Write) register. Thisregister provides control of the write buffering logic. CTRLW bits 7, 3,2, 1 and 0 should always be cleared to 0.

SWEN—bit 6—Synchronized Write Enable “1” enables synchronized writeenable, causing changes by control bit WRRQ (0Ah.2) to be delayed untilthe end of the next block sync. “0” disables synchronized write enable.Selecting synchronized write enable causes the writing of incomingserial data to the buffer RAM to start or stop at the end of the nextblock sync. This prevents the writing of partial blocks into the RAM.SWEN should be changed only during decoder initialization. Write enableand disable is still controlled by bit WRRQ in register CTRL0 (0Ah.2).SWEN synchronizes changes in WRRQ to the end of sync, instead ofrandomly. SWEN is cleared to 0 by hardware reset or firmware reset.

SDSS—bit 5—Subcode-DSP Sync Synchronization “1” enables subcode-DSP syncsynchronization, causing audio write enables by control bit WRRQ (0Ah.2)to be delayed until the first left-channel lower-byte following the endof the subcode block. “0” disables subcode-DSP sync synchronization.Selecting Subcode-DSP Sync Synchronization causes the writing ofincoming serial audio (red book) to the buffer RAM to start at the firstleft-channel lower-byte following the end of the subcode block. Thisprevents separate decoder and subcode interrupts from occurring. SDSSshould be changed only during decoder initialization. Write enable anddisable is still controlled by bit WRRQ in register CTRL0 (0Ah.2). SDSSsynchronizes changes in WRRQ to the subcode block, instead of randomly.SDSS is cleared to 0 by hardware reset or firmware reset.

DCLKE—bit 4—DSP Clock Enable “1” enables the incoming clock from theDSP. “0” disables the incoming clock from the DSP. DCLKE should be sethigh whenever DECEN in register CTRL0 is set high.

FIG. 32 is a description of CRTRG (Correction Retry Trigger) Writing 00hor 01h to register CRTRG triggers an error-correction retry.

CRTRL—bit 0—Correction Retry Register Load “1” loads any updated E01RQ,QRQ, or PRQ values that have been written to register CTRL0 (0Ah.5,1,0)into the ECC sequencer, allowing the correction sequence to be changed.“0” does not load updated E01RQ, QRQ, or PRQ values into the ECCsequencer. Instead, the sequence of the last correction try is repeated.

FIGS. 33 through 38 are descriptions of SUBH0 to SUBH3 (SubheaderRegisters). These registers provide the subheader of each CD-ROM block,and operate similarly to header registers HEAD0-3. If control bit DECENin register CTRL0 (0Ah.7) is enabled, data from the four pairs of bytesfollowing each header (bytes 16–23) is automatically stored in thesubheader registers (SUBH0-3). Bytes 16–23 are stored regardless of thesetting of control bit MODRQ in register CTRL1 (0Bh.3), but the bytescontain subheader data only if mode 2 is selected (MODRQ=1). Duringdisk-monitor operation (see the description of register CTRL0),uncorrected subheader bytes are taken directly from incoming serialdata. If the incoming serial data is buffered, subheader bytes are takenfrom the buffer RAM, and are corrected if form 1 (mode 2) is selectedand ECC is enabled. In either case, SUBH0-3 should be read soon afterthe decoder interrupt occurs (bit DECIb in register IFSTAT becomes 0).SUBH0-3 remains valid until the next sync occurs (see the description ofregister STAT3 for checking the valid time period). The following figureshows the relationship between erasure flags and the byte numbers thatare stored in SUBH0-3 (erasure flags are provided through input pinC2PO.

FIG. 39 is a description of Subheader Byte Number Table. SUBH0-3 areundefined following hardware reset or firmware reset.

FIG. 40 is a description of VER (Version) register. VER contains theversion identification of the device. This register permits expansionand increased performance capabilities for future versions of thecontroller. VER is not changed by hardware reset or firmware reset.

XTAL (Xtal) register provides control of the crystal frequency dividers.

MCK1—bit 3—Pin MCK 1×“1” sets the clock output at pin MCK to the crystalfrequency (no divider). “0” sets the clock output at pin MCK to ½crystal frequency. MCK1 is cleared to 0 by hardware reset, but is notchanged by firmware reset.

XTALD2—bit 0—Crystal Divided by 2 “1” sets the internal controller clockto ½ crystal frequency. “0” sets the internal clock to the crystalfrequency (no divider). XTALD2 is cleared to 0 by hardware reset, but isnot changed by firmware reset.

FIG. 41 is a description of DSPSL (DSP Selection) register. Thisregister selects the DSP configuration.

C2ML—bit 7—C2 MSB to LSB “1” sets the direction of incoming erasures atpin C2PO to upper erasure followed by lower erasure. “0” sets thedirection to lower erasure followed by upper erasure. C2ML is cleared to“0” by hardware reset, but is not changed by firmware reset.

SEL160—bit 6—Select 16 Offset “1” selects 16 bit-clocks per channel,with offset by one after LRCK. “0” does not select 16 bit-clocks withoffset. SEL160 is cleared to “0” by hardware reset, but it is notchanged by firmware reset.

LCHL—bit 5—Left Channel Polarity “1” selects left channel as active ifpin LRCK is “1” “0” selects left channel is active if pin LRCK is “0”.LCHO is set to “1” by hardware reset, but is not changed by firmwarereset.

SEL16—bit 2—Select 16 “1” selects 16 bit-clocks per channel. “0” doesnot select 16 bit-clocks. SEL16 is set to “1” by hardware reset, but isnot hanged by firmware reset.

DIR—bit 1—Data Direction “1” selects the rising edge of DBCK forlatching incoming data at pin DSDATA. “0” selects the falling edge ofDBCK for latching DSDATA. If the incoming data at pin DSDATA changes atthe falling edge of DDBCK, use the rising edge for latching' if DSDATAchanges at the rising edge of DBCK, use the falling edge for latching.EDGE is set to 1 by hardware reset, but is not chanted by firmwarereset.

FIG. 42 DSP SELECTION TABLE shows the settings for various DSPs. Thedefault setting after hardware reset is 00100101 (Matsushita MN66261).The setting of DSPSL is not changed by firmware reset.

FIG. 43 is a description of the HCON/UACL register.

FIG. 44 is a description of the DSPSL register.

FIGS. 45, 46 and 47 are descriptions of the UACL, UACH and UACUMicrocontroller-RAM Address Counter which forms a 20-bit counter thatcontrols the buffer address for transfers between the microcontrollerand RAM. The counter can be set to any physical location in the bufferRAM, and contains enough bits to support larger RAM sizes in futurerevisions. After waiting for busy flag URTBSY to be low in registerHDDIR (1Fh.7), the microcontroller writes the RAM starting address intothe counter. UACL, UACH, and UACU are incremented automatically eachtime a byte is read or written. See the description of registers RAMRD,(1Eh), RAMWR (1Eh), and flag URTBSY in register HDDIR (1Fh.7). UACHshould always be written after UACL is written, and UACU should alwaysbe written after UACH is written. UACL, UACH and UACU are undefinedfollowing hardware reset or firmware reset.

FIG. 48 is a description of the RAMRD/RAMWR RAM Read and Writeregisters. The microcontroller accesses the buffer RAM by reading fromthe RAMRD register or writing to the RAMWR register. To initialize aread or write sequence, the microcontroller waits for busy flag URTBSYto be low in register HDDIR (1Fh.7), then writes the RAM startingaddress into the counter formed by UACL (1Ch), UACH (1Dh), and UACU(2Dh). Reading RAMRD causes events (1), (2) and (3) to occur in thefollowing order: (1)—data previously stored in RAMRD is transferred tothe microcontroller; (2)—RAM data at the counter address is transferredto the RAMRD register; and (3) counter UACL, UACH, and UACU isincremented and flag URTBSY cleared. After the RAM starting address iswritten to the counter, the first read of register RAMRD will transferan INVALID byte to the microcontroller, followed by the starting bytefrom the RAM to the RAMRD register. The invalid byte remains from aprevious access, or from power-up. Because the counter is automaticallyincremented, sequential reads can be used without writing new addressesinto UACL, UACH, and UACU. However, flag URTBSY should be checked beforeeach sequential read from RAMRD to make sure that events (1), (2) and(3) in the previous transfer from RAM to RAMRD have completed.

Writing RAMWR causes the following events to occur in the followingorder: (1)—data is transferred from the microcontroller to registerRAMWR; (2)—data is transferred from RAMWR to the RAM (at the counteraddress); and (3)—counter UACL, UACH and UACU is incremented and flagURTBSY is cleared. After the RAM starting address is written to thecounter, the first write to register RAMWR will transfer a VALID byte tothe RAM. Because the counter is automatically incremented, sequentialwrites can be used without writing new addresses into UACL, UACH andUACU. However, flag URTBSY should be checked before each sequentialwrite to RAMWR to make sure that events (1)–(3) in the previous transferfrom RAMWR to RAM have completed. The contents or RAMRD and RAMWR areundefined following hardware reset or firmware reset.

FIG. 49 is a description of HDDIR Host data Direction Register. Thisregister provides microcontroller and host transfer flags and control.

URTBSY—read bit 7—Microcontroller to RAM Transfer Busy “1” indicatesthat the previous microcontroller-RAM transfer is in progress. “0”indicates that the microcontroller-RAM transfer logic is not busy.URTBSY is cleared to 0 by hardware reset or firmware reset.

CS13—read bit 6 Chip Select 1 and 3 “1” indicates that input pins CS1FX- and CS3FX-became active at the same time, indicating present of anon-ATA host adaptor. “0” indicates normal operation. Flag CS13 can beused to support non-ATA host adapters that have lines CS1FX- andCS3FX-connected together. With this adaptor configuration, host writesto the ATAPI Features Register (1F1) will set flag CS13, allowingfirmware to respond appropriately to adapters that do not supportseparate CS3FX-addressing. CS13 is cleared to 0 by hardware reset, butis not changed by firmware reset.

UDTRG and UDATA—write bits 7 and 6—Microcontroller Data Trigger/Selectare normally set to “0”, selecting data transfers from the buffer RAM tothe host. Setting UDATA to “1” enables microcontroller writes to dataregisters UDTA0-7 (40h-47h), and allows high-speed 8-bit or 16-bit datatnansfers from UDTA0-7 to the host. Writing to UDTRG triggers thetransfer from UDTA0-7 to the host. This type of transfer is efficientfor the small amounts of data (up to eight bytes can be transferred at atime). Registers IFSTAT, IFCTRL, DBCL, DBCH, DTTRG, and DTACK (01h-03h,06h and 07h) are used in the same way as a RAM to host transfer, exceptflag DTENb in IFSTAT has no meaning. However, registers DACL and DACHare not used. After enabling control bit DOUTEN (in register IFCTRL),loading DBCL, DBCH and setting UDATA to 1, and writing to registersUDTA0-7, the microcontroller writes to register DTTRG. Next, themicrocontroller sets UDTRG to 1, followed by 0, to trigger theFIFO-ready transfer logic. The host will receive data beginning withUDTA0 and ending with UDTA7. UDTRG and UDATA are cleared to 0 byhardware reset or firmware reset.

HOST16—write bit 5—Host 16-bit Select “1” selects 16-bit Data reads andPacket FIFO writes (at host register 1F0h). “0” selects 8-bit Data readsand packet-FIFO writes because 8-bit data transfers do not conform tothe ATAPI specification, HOST16 should normally be set to 1. HOST16 iscleared to 0 by hardware reset or firmware reset. Note: For 16-bit datareads, the number of WORDS minus one should be loaded into DBCL andDBCH. For 8-bit data reads, the number of BYTES minus one should beloaded into DBCL and DBCH.

FIG. 50 is a list of the only values that should be written toHDDIR—write bits 4, 3, 2, 1 and 0, following hardware or firmware reset.

FIG. 51 is a description of the HICTL Host Interface Control register.This register provides control of the host interface.

HICTL—bit 7 should only be set to “0”. This bit is cleared to 0 byhardware reset but is not changed by firmware reset.

PDIAGEN—bit 6—Pin HPDIAG- Enable “1” sets pin HPDIAG- to the active-lowstate. “0” clears HPDIAG- to the high-impedance state (HPDIAG- is anopen-drain pin). PDIAGEN is automatically cleared to 0, clearing pinHPDIAG- to high-impedance by hardware reset command Execute DriveDiagnostics (ATA opcode 90h), or ATA Soft Reset (SRST). After PDIAGEN isautomatically cleared, pin HPDIAG- should be set following the timing inATAPI and ATA specification. Execute Drive Diagnostics and ATA SoftReset clear PDIAGEN even if the drive is not selected in the ATAPI DriveSelect Register. PDIAGEN is not changed by firmware reset.

DASPEN—bit 5—Pin HDASP- Enable “1” sets pin HDASP- to the active-lowstate. “0” clears HDASP- to the high-impedance state (HDASP- is an opendrain pin). DASPEN is automatically cleared to 0, clearing pin HDASP- tohigh-impedance by hardware reset command Execute Drive Diagnostics (ATAopcode 90h), or ATA Soft Reset (SRST). After DASPEN is automaticallycleared, pin HDASP- should be set following the timing in ATAPI and ATAspecification. Execute Drive Diagnostics and ATA Soft Reset clear DASPENeven if the drive is not selected in the ATAPI Drive Select Register.DASPEN is not changed by firmware reset.

CLRBSY—bit 4—Clear BSY “1” prepares the clearing logic for flag BSY inthe ATAPI Status Register. Note: BSY is actually cleared by theFOLLOWING write to register HICTL. “0” should be written to CLRBSYduring the FOLLOWING write. Whenever flag BSY in the ATAPI StatusRegister (1F7h) is set, whether automatically or by control bit SETBSY,BSY should be cleared (using CLRBSY) as soon as allowed by the ATAPI andATA specifications. See the description of control bit SETBSY. CLRBSY isnot changed by firmware reset.

SETBSY—bit 3—Set BSY “1” prepares the setting logic for flag BSY in theATAPI Status Register. Note: BSY is actually set by the FOLLOWING writeto register HICTL. “0” should be written to SETBSY during the FOLLOWINGwrite. Writing 1 to SETBSY activates the microcontroller interrupt, ifenabled by control bit IDEIEN in register UMISC (2Eh.7). Flag BSY isautomatically set, and the microcontroller interrupt activated, byhardware reset, command Execute Drive Diagnostics (ATA opcode 90h), ATASoft Reset (SRST), or any command written to the ATAPI Command Register(host register 1F7h). SETBSY and flag BSY are not changed by firmwarereset.

SCOD—bit 2—Select command Packet or Data “1” selects the Command-PacketFIFO to be addressed by the ATA data port (host address 1F0h). “0”selects the buffer RAM to be addressed by the ATA data port. SCOD iscleared to 0 by hardware reset, but is not changed by firmware reset.IORDYEN—bit 1—Pin IORDY Enable “1” allows the data transfer logic tode-assert pin IORDY whenever necessary. “0” does not allow IORDY to bede-asserted IORDY acts as an open-drain pin). If IORDYEN is set high,pin IORDY will be de-asserted to 0 whenever it is necessary to slow downthe data transfer rate to match the capability of the CD-ROM drive. Thecapability of the drive depends on the RAM configuration and crystalfrequency. Note Some systems will not work properly if pin IORDY isde-asserted IORDYEN is set to 1 by hardware reset but is not changed byfirmware reset.

IOCS 16EN—bit 0 Pin IOCS 16- Enable “1” allows pin IOCS 16- to becomeactive low during 16-bit reads from the buffer RAM or 16-bit writes tothe Packet FIFO (at host register 1F0h). Note: Control bit HOST16 inregister HDDIR (1Fh.5) must also be enabled. “0” does not allow IOCS16-to be asserted (IOCS16- is an open drain pin). Because both IOCS 16ENand HOST16 must be enabled to allow assertion of pin IOCS 16-, IOCS 16ENcan always be set to 1. In this case, HOST16 will correctly control pinIOCS16- and all 16-bit transfer logic. To conform to the ATAPIspecification, 16-bit data transfers should be used. IOCS16EN is clearedto 0 by hardware reset, but is not changed by firmware reset.

FIG. 52 is a description of SUBC2 Subcode Control-2 register. Thisregister provides control of the subcode interface.

NOPQ—bit 3 No P-data or Q-data, “1” clears (to 0) bits 7 and 6 (P-dataand Q-data) of subcode data that is written to the buffer RM. “0” allowsthe P-data and Q-data bits to be included in subcode data that iswritten to the buffer RAM. NOPQ is cleared to 0 by hardware reset, butis not changed by firmware reset.

FIG. 53 is a description of the DSP Subcode Clock TABLE.

CDSP2, CDSP1, and CDSP0—bits 2, 1 and 0—DSP Subcode Clock Select, ifsubcode is buffered the DSP clock select bits must be set as shown inthe figure, in order to match the subcode data rate. Only thecombinations shown in the table should be used. DSP2-0 only controlsubcode clocking logic, and do not need to be set unless subcode iswritten to the buffer RAM. CDSP2-0 are cleared to 0 by hardware reset,but are not changed by firmware reset.

FIG. 54 is the STATS Status of subcode register. If read from, STATSprovides status of the subcode interface. If written to, STATS clearsthe subcode interrupt (if enabled) and status flags.

STATS bits 7, 6, 5, 4 and 3 are undefined. During reads of STATS by themicrocontroller, bits 7-3 are undefined, and can be high or low.

MISSY—bit 2—Missing Subcode Sync “1” indicates a missing subcode synccondition. “0” indicates subcode sync is not missing. Flag SINT inregister RSSTAT (2Fh.4) is set (to 1) whenever flag MISSY is set. Ifenabled by control bit SCIEN in register SUBCD (2Ch.4), amicrocontroller interrupt is also activated when MISSY is set. SINT,interrupt, and MISSY are cleared by writing any value to STATS.

SBKEND—bit 1—Normal End of Subcode Block “1” indicates a normal subcodeblock end. “0” indicates no normal subcode block end. Flag SINT inregister RSSTAT (2Fh.4) is set (to 1) whenever flag SBKEND is set. Ifenabled by control bit SCIEN in register SUBCD (2Ch.4), amicrocontroller interrupt is also activated when SBKEND is set. SINT,interrupt, and SBKEND are cleared by writing any value to STATS.

SILSY—bit 0—Illegal Subcode Sync “1” indicates a normal subcode blockend. “0” indicates no normal subcode block end. Flag SINT in registerRSSTAT (2Fh.4) is set (to 1) whenever flag SILSY is set. If enabled bycontrol bit SCIEN in register SUBCD (2Ch.4), a microcontroller interruptis also activated when SILSY is set. SINT, interrupt, and SILSY arecleared by writing any value to STATS.

FIGS. 55 and 56 are descriptions of DBACL and DBACH Data Transfer BlockRegisters. In order to free the microcontroller from calculating2352-byte address boundaries, the buffer RAM is partitioned into blocks.Registers DBACL and DBACH control the RAM block number of the data to betransferred, while counters DACL and DACH (04h and 05h) control theaddress relative to the beginning of the RAM block specified by DBACLand DBACH. The RAM block number is not incremented automatically, andmust be set before each block transfer to the host begins. DBACL andDBACH contain enough bits to support larger RAM sizes in futurerevisions. For data transfer information, see the description ofregisters IFCTRL, DBCL, DBCH, a=DACL, DACH DTTRG, and DTACK (01h- 07h).DBACH should always be written after DBACL is written. DBACL, DBACH arecleared to 00,00h by hardware reset or firmware reset.

FIGS. 57 and 58 are descriptions of SBKL and SBKH Subcode Write BlockRegisters. After the appropriate interrupt occurs, registers SBKL andSBKH point to the RAM block number of subcode that is available fortransfer to the host. Also, the number in SBKL and SBKH plus 1 points tothe RAM block number of the buffer area for writing incoming subcode.Register SBADR (23h) controls the write location within each block. TheRAM block number in SBKL and SBKH is incremented automatically, and onlyneeds to be updated by the microcontroller in order to overwrite adiscarded block. SBKL and SBKH contain enough bits to support larger RAMsizes in future revisions. If subcode sync and data sync aresynchronized by enabling control bit SDSS in register CTRLW (10h.5),SBKL and SBKH should be read soon after the decoder interrupt occurs(bit DEClb in register IFSTAT becomes 0). In this case, SBKL and SBKHremain valid until the next data sync occurs (see the description ofregister STAT3 for checking the valid time period). If subcode sync anddata sync are not synchronized, SBKL and SBKH should be read soon afterthe subcode interrupt occurs (bit MISSY, SBKEND, or SILSY in registerSTATS becomes 1). In this case, SBKL and SBKH remain valid until thenext subcode interrupt occurs. The value read from the lower 9 bits ofSBKL and SBKH during the valid time period identifies the RAM block thatis available for transfer to the host. During reads of SBKH by themicrocontroller, bits 7-1 are undefined, and can be high or low. SBKH,SBKL are cleared to 00,00h by hardware reset or firmware reset, causingbuffering of incoming subcode data to begin at block number 1.

FIGS. 59 and 60 are descriptions of WBKL and WBKH Decoder andBuffer-Write Block Counter registers. In order to free themicrocontroller from calculating 2352-byte address boundaries, thebuffer RAM is partitioned into blocks. Registers WBKL and WBKH point tothe RAM block number of the data to be processed by the error correctionlogic. Also, the number in WBKL and WBKH plus 1 points to the RAM blocknumber of the buffer area for writing incoming serial data. RegistersWAL and WAH (08h/0Ah and 09h/0Bh) control the write location within eachRAM block. The RAM block number in WBKL and WBKH is incrementedautomatically, and only needs to be updated by the microcontroller inorder to overwrite a discarded block. WBKL and WBKH contain enough bitsto support larger RAM sizes in future revisions. WBKL and WBKH should beread soon after the decoder interrupt occurs (bit DECIb in registerIFSTAT becomes 0). WBKL and WBKH remain valid until the next sync occurs(see the description of register STAT3 for checking the valid timeperiod). The value read from the lower 9 bits of WBKL and WBKH duringthis valid time period identifies the RAM block that is available fortransfer to the host. During reads of WBKH by the microcontroller, bits7-1 are undefined, and can be high or low. WBKH, WBKL are cleared to00,00h by hardware reset or firmware reset, causing buffering ofincoming serial data to begin at block number 1.

FIG. 61 is a description of RAMCF RAM Configuration Register. Thisregister provides control of the RAM interface configuration. Eachcontrol bit written to this register can also be read by themicrocontroller.

RFTYP—bit 7 Refresh Type “1” selects CAL before RAM DRAM refresh. “0”selects CAS only DRAM refresh. RFTYP is cleared to 0 by hardware reset,but is not changed by firmware reset.

RAMCLR—bit 6—RAM Clear Enable “1” enables RAM clearing, filling alllocations in the buffer RAM. “0” disables RAM clearing. To clear theRAM, first write the clear data value (normally 00h) to register RAMWR(1Eh). Next, write 00h to registers UACL, UACU, and UACH (1Ch, 1Dh and2Dh). Enable RAMCLR to begin writing the contents of RAMWR to each RAMlocation. When all RAM locations have been filled, RAM0 (bit 5) willchange from 0 to 1. After RAM clearing has completed, themicrocontroller should clear RAMCLR to 0. RAM0 will return to 0 whenRAMCLR is disabled. If enabled by control bit RPEN, the correct paritybit will be written to all locations during RAM clearing. RAMCLR iscleared to 0 by hardware reset, but is not changed by firmware reset.

RAM0—bit 5—RAM Clear Flag (read only) “1” indicates that the RAM addresshas wrapped around beyond 00,00,00h, and that RAM clearing hascompleted. “0” indicates that the RAM clearing has not completed or isdisabled. RAM0 is cleared to 0 by hardware reset, but is not changed byfirmware reset.

UHILO—bit 4—Host High-Low Swap “1” enables byte swaps for reads from thebuffer RAM to the host, causing odd bytes to be read before even bytes.“0” disables byte swap, causing even bytes to be read before odd bytes.Byte swapping is not normally needed for ATAPI operation. UHILO iscleared to 0 by hardware reset, but is not changed by firmware reset.

RPEN—bit 3 RAM Parity Enable “1” enables parity checking, and parityinterrupt, of DRAM data. “0” disables parity checking and parityinterrupt. Enabling RAM parity allows defective DRAMS to be detected.RAM clearing, using control bit RAMCLR, should be completed before RAMparity is enabled. If a parity error is detected, flag PARINT will beset to 1 in register RSSTAT (2Fh.3) and the microcontroller interruptpin will be activated. Flag PARINT and the interrupt are cleared byclearing RPEN to 0. RPEN is cleared to 0 be hardware reset, but is notchanged by firmware reset.

FIG. 62 is a table of RCF2, RCF1 and RCF0—bits 2, 1 and 0—RAMConfiguration. Only the settings shown in the RAM Configuration Tableshould be used. RCF2, RCF1, and RCF0 are cleared to 0 by hardware reset,but are not changed by firmware reset.

FIG. 63 is a description of MEMCF (Memory Layout Configuration)register. This register provides control of the RAM layoutconfiguration.

MEMCF bits 7, 6, 5, and 4 must always be set to 0. MEMCF bits 7, 6, 5,and 4 are cleared to 0 by hardware reset, but are not changed byfirmware reset.

PURG—bit 3—Data FIFO Purge “1” purges the RAM to Host Data FIFO. “0”disables the FIFO purge logic. This bit should be cleared to 0 exceptduring the purge operation. PURG is cleared to 0 by hardware reset, butis not changed by firmware reset.

IORDYF—bit 2—Pin IORDY Fast Enable “1” enables output pin IORDY to bede-asserted to 0 without qualification by input pin HRD-. “0” disablesunqualified de-assertion of pin IORDY. This bit speeds up de-assertionof pin IORDY by ignoring the state of pin HRD-. However, unqualifiedde-assertion of IORDY violates the ATA specification, and may interferewith normal operation of many systems. IORDYF is cleared to 0 byhardware reset, but is not changed by firmware reset.

FIG. 64 is a description of MLY1 and MLY0—bits 1 and 0—Memory LayoutConfiguration. Following hardware reset, the memory layout configurationshould be set as shown in the figure. Only the settings shown in theMemory Layout Configuration Table should be used. Normally, allauxiliary blocks are buffered (MLY1=1 and MLY0=1). If only the last 2auxiliary blocks are buffered, the configuration must be changedwhenever data transfer sizes above 2048 bytes are required. MLY1 andMLY0 ARE CLEARED TO 0 BY HARDWARE RESET, but are not changed by firmwarereset.

FIG. 65 is a description of SUBCD Subcode Control register. Thisregister provides control of the subcode interface.

SBXCK—bit 7—Subcode External Clock “1” selects an external clock frompin EXCK to be used by the subcode logic. “0” selects an internal clockto be used by the subcode logic. SBXCK is cleared to 0 by hardwarereset, but is not changed by firmware reset.

SCEN—bit 6—Subcode Enable “1” enables the subcode logic. “0” disablesthe subcode logic. SCEN is cleared to 0 by hardware reset, but is notchanged by firmware reset.

SCKB2—bit 5—Subcode Clock Divide By 2 “1” enables the divide by 2 logic(for internal or external clock). “0” disables the divide by 2 logic.SCKB2 is cleared to 0 by hardware reset, but is not changed by firmwarereset.

SCIEN—bit 4—Subcode Interrupt Enable “1” enables activation of subcodeinterrupts to the microprocessor. “0” disables subcode interrupts. SCIENis cleared to 0 by hardware reset, but is not changed by firmware reset.

EXINV—bit 3—External Clock Invert Select “1” selects an inverted outputclock at pin EXCK if EXCK is set as an output. “0” selects anon-inverted clock. EXINV is cleared to 0 by hardware reset, but is notchanged by firmware reset.

EXOP—bit 2—Pin EXCK Operation “1” sets EXCK as an output pin. “0” setsEXCK as an input pin. EXOP is cleared to 0 by hardware reset, but is notchanged by firmware reset.

FIG. 66 is SBSEL1 and SBSEL0—bits 1 and 0—Subcode Format Select Table.The subcode format should be set according to the figure. SBSEL1 andSBSEL0 are cleared to 0 by hardware reset, but are not changed byfirmware reset.

FIG. 67 is a description of UMISC (Miscellaneous MicrocontrollerControl) register. This register provides miscellaneous flags andcontrol bits.

PDIAGb—read-bit 1—Pin HPDIAG- Flag “1” indicates that open-drain pinHPDIAG- is high (inactive). In this case, both master and slave drivesare de-asserting pin HPDIAG-. “0” indicates that pin HPDIAG- is low(active) In this case, either the master or slave drive is setting pinHPDIAG- to active-low.

DASPb—read-bit 0—Pin HDASP- Flag “1” indicates that open-drain pinHDASP- is high (inactive). In this case, both master and slave drivesare de-asserting pin HDASP-. “0” indicates that pin HDASP- is low(active). In this case, either the master or slave drive is setting pinHDASP- to active-low.

IDEIEN—write-bit 7—IDE Interrupt Enable “1” enables activation of IDE(ATA) interrupts to the microprocessor. “0” disables activation of IDE(ATA) interrupts. IDE interrupts (if enabled) are activated, and flagSRST, CMD, DIAGCMD, or HRST set in register RSSTAT (2Fh.7,6,5,0),whenever the BSY flag in the ATAPI status register is set automaticallyby: 1 written to bit SRST (Soft Reset) in the ATAPI Device ControlRegister (host address 3F6h) in the master or slave drive. Note: The BSYflag and IDE interrupt (if enabled) cannot be cleared while SRST is setto 1. Any command written to the ATAPI Command Register (host address1F7h) while the drive is selected. Command Execute Drive Diagnostics(ATA opcode 90h) written to the master or slave drive. Note: if opcode90h is written while the drive is selected, both flags CMD and DIAGCMDwill be set.

Hardware Reset (however, hardware reset clears IDEIEN). Writing 1followed by 0 to SETBSY in register HICTL (20h.3) sets BSY and activatesthe interrupt (if enabled by IDEIEN) but does not set a status flag. TheBSY flag and IDE interrupt are cleared by writing 1 followed by 0 tocontrol bit CLRBSY in register HICTL (20h.4). IDEIEN is cleared to 0 byhardware reset, but is not changed by fuimware reset.

UMISC write-bit 6 should always be cleared to 0.

DRVEb—write-bit 5—Drive Enable “1” disables selection of the drive,whether bit DRV in the ATAPI Drive Select Register (host address 1F6h)is 0 or 1. “0” enables selection of the drive if bit DRV matches thesetting of DRV1b in register UMISC. DRVEb is set to 0 (active) byhardware reset, but is not changed by firmware reset.

DRV1b—write-bit 4—Drive 1 “1” sets the drive to be selected when bit DRVin the ATAPI Drive Select Register is set to 0 (drive 0). “0” sets thedrive to be selected when bit DRV in the ATAPI Drive Select Register isset to 1 (drive 1). DRV1b is set to 0 (drive 1) by hardware reset, butis not changed by firmware reset.

HINTRQ—write-bit 3—Host Interrupt Request “1” sets pin HIRQ high if thedrive is selected and NIEN (Interrupt Enable) is enabled in the ATAPIDevice Control Register (host address 3F6h). “0” clears pin HIRQ (to 0)if the drive is selected and NIEN is enabled. HINTRQ is automaticallycleared to 0 by the following: Hardware reset, 1 written to bit SRST(Soft Reset) in the ATAPI Device Control Register (host address 3F6h) inthe master or slave drive, any command written to the ATAPI CommandRegister (host address 1F7h) while the drive is selected, and a readfrom the ATAPI Status Register (host address 1F7h) while the drive isselected. HINTRQ is not changed by firmware reset, or by reads from theATAPI Alternate Status Register (host address 3F6h). If the drive is notselected, or if NIEN is disabled (cleared to 1), pin HIRQ becomeshigh-impedance.

UMISC write-bits 2, 1, and 0 should always be set to 0.

FIG. 68 is a description of RSSTAT—Reset, IDE, and Subcode StatusRegister.

RSSTAT (Reset, IDE, and Subcode Status) register provides status flagsfor reset, IDE, and subcode logic.

SRSTF—bit 7—Soft Reset Flag “1” indicates that 1 has been written to bitSRST (Soft Reset) in the ATAPI Device Control Register (host address3F6h) in the master or slave drive. “0” indicates that 1 has not beenwritten to bit SRST. The BSY flag is set, and IDE interrupt to themicrocontroller activated (if enabled), whenever SRST is set. BSY andIDE interrupt cannot be cleared until SRST is cleared to 0 (however, theIDE interrupt can be disabled). After SRST is cleared, the BSY flag andIDE interrupt are cleared by writing 1 followed by 0 to control bitCLRBSY in register HICTL (20h.4). Flag SRSTF is cleared to 0 by hardwarereset, but is not changed by firmware reset.

CMD—bit 6—ATA Command “1” indicates that a command has been written tothe ATAPI Command Register (host address 1F7h) while the drive wasselected. “0” indicates that a command has not been written. The BSYflag is set, and IDE interrupt to the microcontroller activated (ifenabled), whenever a command is written to the ATAPI Command Registerwhile the drive is selected. The BSY flag and IDE interrupt are clearedby writing 1 followed by 0 to control bit CLRBSY in register HICTL(20h.4). CMD is cleared to 0 by hardware reset, but is not changed byfirmware reset.

DIAGCMD—bit 5—Execute Drive Diagnostics Command “1” indicates that theATA command Execute Drive Diagnostics (ATA opcode 90h) has been writtento the master or slave drive. “0” indicates that Execute DriveDiagnostics has not been written. The BSY flag is set, and IDE interruptto the microcontroller activated (if enabled), whenever Execute DriveDiagnostics is Written to the ATAPI Command Register. If opcode 90h iswritten while the drive is selected, both flags CMD and DIAGCMD will beset. The BSY flag and IDE interrupt are cleared by writing 1 followed by0 to control bit CLRBSY in register HICTL (20h.4). DIAGCMD is cleared to0 by hardware reset, but is not changed by firmware reset.

SINT—bit 4—Subcode Interrupt Flag “1” indicates that flag MISSY, SBKEND,or SILSY has been set in register STATS (22h.2,1,0). “0” indicates thatflag MISSY, SBKEND, or SILSY has not been set. If enabled by control bitSCIEN in register SUBCD (2Ch.4), a microcontroller interrupt isactivated when SINT is set. SINT, interrupt, and the flag in registerSTATS are cleared by writing any value to STATS. SINT is cleared to 0 byhardware reset or firmware reset.

PARINT—bit 3—Parity Interrupt Flag “1” indicates that a parity error hasbeen detected in the DRAM. “0” indicates that a parity error has notbeen detected. If enabled by control bit RPEN in register RAMCF (2Ah.3),a microcontroller interrupt is activated when PARINT is set. PARINT andthe interrupt are cleared by writing 0 to RPEN. PARINT is cleared to 0by hardware reset, but is not changed by firmware reset.

RST—bit 2—Reset Flag “1” indicates that the device is currently beingreset. “0” indicates that the device is not currently being reset. RSTallow the hardware reset to be monitored (if the microcontroller is notreset at the same time).

URST—bit 1—Firmware Reset Flag “1” indicates that the current or mostrecent reset was activated by writing to the register RESET (0Fh). “0”indicates that register RESET has not been active. The first read ofRSSTAT following the end of the firmware reset cycle clears URST to 0.URST is cleared to 0 by hardware reset.

HRST—bit 0—Hardware Reset Flag indicates that the current or most recentreset was activated by hardware reset (pin RESET-). “0” indicates thatpin RESET- has not been set to 0. The BSY flag is set whenever hardwarereset is activated. The BSY flag and IDE interrupt are cleared bywriting 1 followed by 0 to control bit CLRBSY in register HICTL (20h.4).The first read of RSSTAT following the end of the hardware reset cycleclears HRST to 0. HRST is not changed by firmware reset.

FIGS. 69–75 are descriptions of ATAPI Task File Registers (TR). The TaskFile register bits are labeled according to the ATAPI Specification.FIG. 69 is a description of ATFEA and ATERR.

ATFEA—Output from Features TR—The host writes this register at hostaddress 1F1h.

ATERR—Input to Error TR—The host reads this register at host address1F1h.

FIG. 70 is a description of ATINT—I/O of Interrupt Reason TR—The hostaccesses this register at host address 1F2h. (1F2h is Sector Count inATA Specification.)

FIG. 71 is a description of ATSPA—Spare TR (unused in ATAPISpecification)—The host accesses this register at host address 1F3h.(1F3h is Sector Number in ATA Specification.)

FIG. 72 is a description of ATBLO—I/O of Byte Count Low TR—The hostaccesses this register at host address 1F4h. (1F4h is Cylinder Low inATA Specification.)

FIG. 73 is a description of ATBHI—I/O of Byte Count High TR—The hostaccesses this register at host address 1F5h. (1F5h is Cylinder High inATA Specification.)

FIG. 74 is a description of ATDRS—I/O of Drive Select TR—The hostaccesses this register at host address 1F6h. Bit 4, DRV, selects drive 1when high or drive 0 when low. Bit 6, L, should be set to 1 to selectLBA (not CHS) addressing. Bit 4 (DRV) is set to 1 by hardware reset.(1F6h was Drive/Head Select in ATA Specification.)

FIG. 75 is a description of ATCMD—Output from Command Register—The hostwrites this register at host address 1F7h.

ATSTA—Input to Status Register—The host reads this register at hostaddress 1F7h.

FIGS. 76–83 are descriptions of the Microcontroller to Host DataTransfer Registers. The microcontroller writes up to eight bytes of datato be transferred to UDTA0-7. The host reads these registers as data athost address 1FOh. UDTA0 is read first, and UDTA7 last. See thedescription of control bits UDTRG and UDATA in register HDDIR (1Fh.7,6).

1. An apparatus comprising: a host interface for an optical drive, saidhost interface operable to be directly connected to a host computer viaan IDE/ATA bus, said host interface including, a multi-byte commandbuffer operable, per command, to store sequentially contiguous multiplecommand bytes received from said host computer in a single commandtransfer, the multi-byte command buffer addressed by one of a pluralityof ATA command block register addresses, a drive/head register addressedby another of said plurality of ATA command block register addresses,said drive/head register including a DRV bit, wherein said hostinterface uses said DRV bit to determine whether to store commands insaid multi-byte command buffer, a status register addressed by yetanother of said plurality of ATA command block register addresses, saidstatus register including a BSY bit, circuitry operable to alter saidBSY bit responsive to command events initiated by the host computer,circuitry operable to carry out initial signal transitions on DASP,PDIAG, and HIRQ lines of said IDE/ATA bus in response to soft reset andexecute drive diagnostic command events, and circuitry operable to clearthe signal on the HIRQ line responsive to said host computer readingsaid status register; and a path in said optical drive controlleroperable to allow a microcontroller, which controls reading ofinformation from optical media, to read from said multi-byte commandbuffer, to cause said BSY bit to be altered, to read said DRV bit, andto cause certain transitions of signals on said DASP, PDIAG, and HIRQlines of said IDE/ATA bus.
 2. The apparatus of claim 1, wherein saidplurality of ATA command block register addresses address eight registerlocations.
 3. The apparatus of claim 1, wherein said IDE/ATA busincludes, host address lines; and a host chip select line whose signalidentifies whether signals on the host address lines are carrying one ofsaid ATA command block register addresses.
 4. The apparatus of claim 1,wherein said host interface includes physical registers that areaddressed by at least certain of said plurality of ATA command blockregister addresses.
 5. The apparatus of claim 1, wherein said hostinterface supports all of the signals required by the ATA transferprotocol.
 6. The apparatus of claim 1, wherein said IDE/ATA bus is atleast 16 bits wide.
 7. The apparatus of claim 1, wherein the one of saidplurality of ATA command block register addresses that can be used toaddress the multi-byte command buffer is the address of a data port inthe ATA transfer protocol.
 8. The apparatus of claim 1, wherein saidhost interface also includes a multi-byte data buffer, addressed by theone of said plurality of ATA command block register addresses that canbe used to address the multi-byte command buffer, operable to store datato be transmitted to said host computer.
 9. The apparatus of claim 1,wherein said multi-byte data buffer is a queue or FIFO.
 10. Theapparatus of claim 1, wherein said multi-byte command buffer is a queueor FIFO.
 11. The apparatus of claim 1, wherein said host interface isoperable to assert signals on said DASP and PDIAG lines of said IDE/ATAbus according to the ATA transfer protocol.
 12. The apparatus of claim11, wherein said host interface is also operable to assert signals onsaid HIRQ line of said IDE/ATA bus according to the ATA transferprotocol.
 13. The apparatus of claim 1, wherein said host interface isalso operable to assert signals on said DASP and PDIAG lines of saidIDE/ATA bus responsive to power on reset or execute diagnostic commandsreceived from said host computer.
 14. The apparatus of claim 1, whereinsaid circuitry operable to alter said BSY bit is to alter said BSY bitto indicate that a data-transfer is in process.
 15. An optical diskdrive controller for an optical disk drive to control the communicationof digital information between an optical disk inserted in the opticaldisk drive and a host computer, said optical disk drive including driveelectronics comprising a digital signal processor, a random accessmemory, and a microcontroller, said host computer operable tocommunicate with the optical disk drive controller directly via anIDE/ATA bus according to the ATA transfer protocol, the ATA transferprotocol including a plurality of ATA command block register addresses,the optical disk drive controller comprising: a host interface operableto be coupled to said IDE/ATA bus and including, a multi-byte commandbuffer, addressed by one of said plurality of ATA command block registeraddresses, operable, per command, to sequentially store multiple commandbytes received contiguously from said host computer in a single commandtransfer, a status register addressed by another of said plurality ofATA command block register addresses, said status register including aBSY bit, and a multi-byte data buffer, addressed by the one of saidplurality of ATA command block register addresses that can be used toaddress the multi-byte command buffer, operable to ensure anuninterrupted flow of data from said optical disk drive controller tosaid host computer; and a path operable to allow said microcontroller toread said multi-byte command buffer and alter said BSY bit.
 16. Theapparatus of claim 15, wherein said plurality of ATA command blockregister addresses address eight register locations.
 17. The apparatusof claim 15, wherein said IDE/ATA bus includes, host address lines; anda host chip select line whose signal identifies whether signals on thehost address lines are carrying one of said ATA command block registeraddresses.
 18. The apparatus of claim 15, wherein said host interfaceincludes physical registers that are addressed by at least certain ofsaid plurality of ATA command block register addresses.
 19. Theapparatus of claim 15, wherein said IDE/ATA bus is at least 16 bitswide.
 20. The apparatus of claim 15, wherein the one of said pluralityof ATA command block register addresses that can be used to address themulti-byte command buffer is the address of a data port in the ATAtransfer protocol.
 21. The apparatus of claim 15, wherein saidmulti-byte data buffer is a queue or FIFO.
 22. The apparatus of claim15, wherein said multi-byte command buffer is a queue or FIFO.
 23. Theapparatus of claim 15, wherein said host interface includes circuitryoperable to clear the signal on an HIRQ line of said IDE/ATA busresponsive to said host computer reading said status register.
 24. Theapparatus of claim 15, wherein said host interface includes circuitryoperable to alter said BSY bit, responsive to command events initiatedby the host computer, to a state that indicates a data-transfer is inprocess.
 25. The apparatus of claim 24, wherein said path operable toallow said microcontroller to alter said BSY bit to a state thatindicates that no data-transfer is in process.
 26. The apparatus ofclaim 15, wherein said host interface is operable to assert signals onDASP and PDIAG lines of said IDE/ATA bus according to the ATA transferprotocol.
 27. The apparatus of claim 26, wherein said host interface isalso operable to assert signals on an HIRQ line of said IDE/ATA busaccording to the ATA transfer protocol.
 28. The apparatus of claim 27,wherein said host interface includes circuitry operable to carry outinitial signal transitions on said DASP, PDIAG, and HIRQ lines inresponse to soft reset and execute drive diagnostic command events. 29.The apparatus of claim 28, wherein said microcontroller is also operableto control certain transitions of signals on said DASP, PDIAG, and HIRQlines of said IDE/ATA bus.
 30. The apparatus of claim 15, wherein saidhost interface is also operable to assert signals on DASP and PDIAGlines of said IDE/ATA bus responsive to power on reset or executediagnostic commands received from said host computer.
 31. The apparatusof claim 25, wherein said microcontroller is also operable to cause theassertion of signals on DASP and PDIAG lines of said IDE/ATA bus. 32.The apparatus of claim 15, wherein said host interface includes adrive/head register addressed by yet another of said plurality of ATAcommand block register addresses, said drive/head register including aDRV bit.
 33. The apparatus of claim 32, wherein said host interface usessaid DRV bit to determine whether to store commands in said multi-bytecommand buffer.
 34. The apparatus of claim 15, wherein said hostinterface is also operable to assert signals on an HIRQ line of saidIDE/ATA bus according to the ATA transfer protocol.
 35. The apparatus ofclaim 15, wherein said host interface is also operable to assert signalson an HIRQ line of said IDE/ATA bus to alert said host computer duringdata transfers.
 36. The apparatus of claim 15, wherein said hostinterface is also operable to assert signals on an HIRQ line of saidIDE/ATA bus to allow said host computer to engage in multi-tasking.